home *** CD-ROM | disk | FTP | other *** search
Text File | 1989-06-26 | 1.6 KB | 38 lines | [TEXT/GEOL] |
- Item forwarded by D1716 to MACAPP.TECH$
-
- Item 1068581 18-May-89 11:20
-
- From: D1716 Intelligent Sys Design, G Gump, PRT
-
- To: AED0266 Computer Pros Wayne
-
- Sub: Response to MABuild MacApp
-
- As I write this note I am talking on the phone with our MacApp Gru. He has
- modified 2.0B5 to work with MPW 3.0 and makes the following recomendations:
-
- Compile MacApp with the DeBug on this will generate all the errors in a
- unit (you will do this repeatedly until it compiles), work from the bottom of
- the list up, it will show which variables are problems (the old compiler let
- what amounted to an error slip by), in front of that line of code you set a
- local variable to be equal to the field variable that is causing the error,
- then you change the field variable name in the call to the local variable, then
- add the local variable to the subroutine. Note: there are a few instances
- where you have to exchange the local and field variable back, you will have to
- check the subroutine call as it is defined to see if the value was passed as a
- var. This solution we feel is better than the recomendation of turning off the
- strict type checking of the compiler.
-
- If you have further questions you can call Mike Staley (512) 650 - 3917.
-
- As of the conference 2.0B5 and the documentation with it is the latest, but
- 2.0B9 is "real soon now".
-
- If the MacApp people are listening we would be willing to post a patched
- version of MacApp 2.0B5 if you let us.
-
- George L. Storm
- Intelligent Systems Design
-
-
-